Exchange 2003  mail being sent to the wrong user
Hi, I am having a hugh problem with mail being sent to the wrong users. It is with about a dozen of my 271 users. New MS Server 2003 sp2, Exchange server 2003. Hope this is not too wordy..... Here are my observations so far: I am running Exchange 2003, and I have found that when some folks send mail to one user, it goes to someone else.I have checked the server info on the users, and everything looks correct.When I send and email to the effected users and I check the properties of that user, (in outlook,) it shows that it is being sent to another user.This is happening with random users, and I can find nowhere to make a change. ************* When I add a user to and email (Outlook)via the global address list, I right click on the user and click properties, the dialog box pops up with the username in the banner, and the wrong user information in the fields.I sent a test to the identified users, and the mail gets sent to the bad user, but when I look at his mail, there is nothing there. ****************** log into my outlooksend new mailclick to:browse to use stacyclick the options box select receive and read reciptsend mailI get a message from the Administrator:Your messageTo:Kathrine McGarrySubject:testSent:8/28/2008 10:50 AMwas delivered to the following recipient(s):Kathrine McGarry on 8/28/2008 10:50 AMNow I see this went to another user, not the bad username in the properties box. **************** In an attempt to figure this out, I deleted Brian, he is gone from the Computers and Users space, but his mailbox is still there...I thought I selected to delete him completly, is there an easy way to delete the mailbox?There is not a delete option. When I try to purge, it is greyed out! **************** OK,I downloaded the MAPI editor from MS, when I run it and look at the mail boxes I see the bad users have a PT_STRING8 (PR_EMAIL_ADDRESS) of/O=LITCHFIELDSD/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=GMSLooking at a good user, the srting shoul look like this:/O=LITCHFIELDSD/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=BLAMBERTWhen I try to edit the proerty, it lets me change it, but it will not save it????I can not find a save feature anywhere. ***************** Thanx,
August 29th, 2008 2:04am

This is an entirely new E2K3 organization? Or did you use some type of migration tool to migrate from another organization. The type of problem you are seeing (or at least what I *think* you are seeing) is very rare and only occurs when you have migrated from another Exchange organization. Look on the properties of each of your users at the E-mail Addresses property page. Do your users have X500 addresses? Look at the X500 address and see if the CN= on the end matches the person's alias? Do they have mulitple X500 addresses. Here is some background. Internally, e-mail messages and the address book for internal recipients identify the recipient using a speical (and read-only) attribute called legacyExchangeDN. It is of the form: /O=LITCHFIELDSD/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=BLAMBERT All messages sent and received by internal users have this stamped in the "To" and "From" fields inside the Exchange database. All internal addresses in the Outlook nickname file (the .NK2 file in the user's profile) identify the object in the Global Address List using this "distinguished name" of the object. The NK2 file keeps the "recently used" e-mail addresses for Outlook 2003/2007. When you migrate from another Exchange organization, most migration tools will copy the user's legacyExchangeDN attribute from the old organization and stick it in to the user's E-mail Addresses as a new X500 address. This helps maintain "reply-ability" to old messages and it ensures that user's NK2 files keep working. I have seen very rare situtations where the legacyExchangeDN's get messed up. By the way, editing the legacyExchangeDN property via the MAPI Editor will not work.
Free Windows Admin Tool Kit Click here and download it now
August 31st, 2008 12:30am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics